[Agent Builder] Update access control docs: new agents default to Private - #8232
Merged
Merged
Conversation
charlotte-hoblik
added
documentation
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
Contributor
🔍 Preview links for changed docs⏳ Building and deploying preview... View progress This comment will be updated with preview links when the build is complete. |
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
charlotte-hoblik
marked this pull request as draft
September 7, 2026 22:43
charlotte-hoblik
marked this pull request as ready for review
September 10, 2026 12:42
brunofarache
approved these changes
Sep 16, 2026
brunofarache
left a comment
brunofarache
left a comment
Member
There was a problem hiding this comment.
looks good to me! felt like a bit repetitive that we are explaining public/shared/private access modes in more than one place, but apparently they are in different files/sections.
Contributor
Author
|
Thank you, trimmed the level definitions out of the "Set access control" step, so they're now defined once in #access-control-settings and the step just names the default. |
Contributor
Docs review summaryFocus areas
Nits
Notes
|
leemthompo
approved these changes
Sep 17, 2026
leemthompo
left a comment
leemthompo
left a comment
Member
There was a problem hiding this comment.
Writing LGTM with a couple tiny nits, and a note about applies_to tags and applies-switch
| ``` | ||
|
|
||
| In addition to the three access control levels, you can configure access controls for individual users on a per-agent basis. This allows you to grant specific users view or edit access to an agent, giving you more granular control over who can interact with and modify your agents. | ||
| In addition to the three access control levels, you can grant individual users access to a specific agent. Use this when the base level is too broad or too narrow for a particular person. |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Co-authored-by: Liam Thompson <leemthompo@gmail.com>
Co-authored-by: Liam Thompson <leemthompo@gmail.com>
Co-authored-by: Liam Thompson <leemthompo@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes https://github.com/elastic/docs-content-internal/issues/1609
custom-agents.mdsaid new agents default to Public. kibana#282015 (9.6) changed that to Private. Verifying it turned up three related changes across two minors, so this PR covers the whole access control section rather than one line:9.6+. The old Public default is scoped9.4-9.5. Existing agents and built-in agents are unaffected and stay Public, which is worth stating explicitly.9.4-scoped note for readers still on the old label. Heading anchor redirect added.chat.md: the agent list badge list omitted Private. Also clarified that Read-only marks built-in agents rather than being an access level.kibana-api.md: noted that omittingaccess_controlon create produces a private agent.